-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to set peering options in aws_vpc_peering_connection. #8310
Add ability to set peering options in aws_vpc_peering_connection. #8310
Conversation
Tests are passing:
|
Resolves #8169. Things to do:
|
14dc4af
to
9ef8cbb
Compare
@stack72 over to you 🚀 |
@@ -47,7 +47,9 @@ func resourceAwsVpcPeeringConnection() *schema.Resource { | |||
Type: schema.TypeString, | |||
Computed: true, | |||
}, | |||
"tags": tagsSchema(), | |||
"accepter": vpcPeeringConnectionOptionsSchema(), | |||
"requester": vpcPeeringConnectionOptionsSchema(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love the reuse of schema block here!
This commit adds two optional blocks called "accepter" and "requester" to the resource allowing for setting desired VPC Peering Connection options for VPCs that participate in the VPC peering. Signed-off-by: Krzysztof Wilczynski <[email protected]>
9ef8cbb
to
b435988
Compare
Hi @kwilczynski This LGTM! Thanks for making the changes here :)
P. |
This is causing a terraform crash.
|
It appears like
Perhaps the |
@BSick7 sincere apologies about this! Let me have a look. When I was testing this, I saw that at least in us-east-1 it was always returning the whole structure, for example:
What region have you tried? I am going to do my best to try to reproduce and fix this. |
This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]>
Resolved in #8338. The details about peering options would not be included if the connection is still pending acceptance when the read and/or refresh happens, or when the peering is to be manually accepted (which also means that the request is pending acceptance). @BSick7 sincere apologies for the troubles! |
Fast fix! Thanks @kwilczynski |
@BSick7 thank you! I am sorry that this has caused you some troubles. |
This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]>
This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]>
This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]>
This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]>
This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]>
This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]>
…upersedes #8338) (#8432) * Fix crash when reading VPC Peering Connection options. This resolves the issue introduced in #8310. Signed-off-by: Krzysztof Wilczynski <[email protected]> * Do not de-reference values when using Set(). Signed-off-by: Krzysztof Wilczynski <[email protected]> * provider/aws: Update VPC Peering connect accept/request attributes * change from type list to type set * provider/aws: Update VPC Peering accept/requst options, tests * errwrap some things
…upersedes hashicorp#8338) (hashicorp#8432) * Fix crash when reading VPC Peering Connection options. This resolves the issue introduced in hashicorp#8310. Signed-off-by: Krzysztof Wilczynski <[email protected]> * Do not de-reference values when using Set(). Signed-off-by: Krzysztof Wilczynski <[email protected]> * provider/aws: Update VPC Peering connect accept/request attributes * change from type list to type set * provider/aws: Update VPC Peering accept/requst options, tests * errwrap some things
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This commit adds two optional blocks called "accepter" and "requester" to the
resource allowing for setting desired VPC Peering Connection options for VPCs
that participate in the VPC peering.
Signed-off-by: Krzysztof Wilczynski [email protected]